There are a number of error messages that are logged due to problems within AIX or the Adapter firmware. These errors are not logged due to hardware errors. .
Replacing the Adapter WILL NOT fix the problem these error codes are reporting.
DETAIL SENSE DATA
Here below is a cut from the full error log sense template. Click here to see full error template.
RRRR RRRR EEEE EEEE TTCC OOOO NNNN NNNN NNNN NNNN IIII IIII MMMM MMMM LLLL LLLLAIX Version 5.3 and below
AIX 6 and above:
| Error EEEE EEEE |
What this means | What to do |
| 0x0000 0021 | The AIX device driver is deficient in handling all of the adapter reject codes | Action plan depends on reject code. |
| 0x0000 0023 | The AIX device driver is deficient in handling all of the adapter reject codes | Action plan depends on reject code |
| 0x0000 0028 | An AIX timer has expired and AIX cannot associate it with an event. | This is an AIX device driver issue, contact AIX SAN support.. |
| 0x0000 0029 | This error indicates that a device driver call to an AIX kernel service to D_MAP_LIST failed. . | This is an internal AIX issue, contact AIX SAN support |
| 0x0000 0031 | The AIX device driver received a command form the protocol driver or an application and the requested opcode is unknown. | This an AIX protocol driver or AIX application issue, contact AIX SAN support.. |
| 0x0000 0033 | Indicates the routines in the device driver received requests with bad op-codes from other areas of the device driver or some other driver (protocol),. | contact AIX SAN support. |
| 0x0000 0033 | Indicates the routines in the device driver received requests with bad op-codes from other areas of the device driver or some other driver (protocol). | contact AIX SAN support. |
| 0x0000 0034 | The AIX start routine received a command with an unknown opcode.. | contact AIX SAN support. |
| 0x0000 0035 | Issued when a cmd has been requested and one is outstanding contact AIX support.. | contact AIX SAN support. |
| 0x0000 0036 | The protocol driver or an application has called the driver stub function (no valid function pointer). | This is an AIX problem or an application problem contact AIX SAN support. |
| 0x0000 0037 | The adapter driver failed to open the adapter. This is error is logged when the device driver can not bring the link up. | Do link down problem determination. |
| 0x0000 0038 | The device driver failed to find a free command structure to issue a reply to an ELS cmd. | This may informational only (busy system) or an AIX or SAN issue, if it persists, contact AIX SAN support. |
| 0x0000 0039 | The device driver could not find an async IOCB to send an ELS cmd. These are usually used to send LOGOs (log outs). | This may informational only (busy system) or an AIX or SAN issue, if it persists, contact AIX SAN support.. |
| 0x0000 003A | Received an unsolicited sequence without out a valid buffer | contact AIX SAN support |
| 0x0000 0042 | All attempts to close the adapter have failed. . | Adapter close is an AIX concept, contact AIX SAN support |
| 0x0000 0043 | All attempts to close the adapter have failed. | Adapter close is an AIX concept, contact AIX SAN support |
| 0x0000 0044 | Issued when the protocol driver sends n_port ids of 0 to the device driver. | This is an AIX application or protocol driver issue, contact AIX SAN support. |
| 0x0000 0045 | Issued when the protocol driver sends n_port ids of 0 to the device driver. | This is an AIX application or protocol driver issue, contact AIX SAN support. |
| 0x0000 0047 | While processing a register login mailbox, the AIX log_item structure was found to be null. | contact AIX SAN support. |
| 0x0000 004A | While processing a register login mailbox, the AIX log_item structure was found to be null. | contact AIX SAN support. |
| 0x0000 004B | Register DMA services failed in efc_config. | contact AIX SAN support. |
| 0x0000 004C | Register DMA services failed in efc_init . | contact AIX SAN support. |
| 0x0000 004D | An async cmd on the adapter ring was de-queued but not freed because it was un-tagged. | contact AIX SAN support. |
| 0x0000 004E | els cmd de-queued but found untagged, contact AIX support.. | contact AIX SAN support. |
| 0x0000 0052 | No free buffers available to queue to the adapter, contact AIX support. | contact AIX SAN support. |
| 0x0000 0055 | Received a mailbox command on the slot the has cmd already queued up, contact AIX support.. | contact AIX SAN support. |
| 0x0000 0056 | The eyecatcher check failed while issuing cmd to adapter ring. (level 1 trace), contact AIX support. | contact AIX SAN support. |
| 0x0000 0057 | The eyecatcher check failed while issuing qbuf to adapter ring. (level 1 trace), contact AIX support. | contact AIX SAN support. |
| 0x0000 0060 | Issued when the cmd/IOCB buffer queue problems are encountered, contact AIX support. | contact AIX SAN support. |
| 0x0000 0061 | Issued when the cmd/IOCB buffer queue problems are encountered. | contact AIX SAN support. |
| 0x0000 0062 | Issued when the cmd/IOCB buffer queue problems are encountered. | contact AIX SAN support. |
| 0x0000 0063 | Issued when the cmd/IOCB buffer queue problems are encountered. | contact AIX SAN support. |
| 0x0000 0064 | Issued when the cmd/IOCB buffer queue problems are encountered. | contact AIX SAN support. |
| 0x0000 0065 | Issued when the cmd/IOCB buffer queue problems are encountered. | contact AIX SAN support. |
| 0x0000 0066 | Issued when the cmd/IOCB buffer queue problems are encountered. | contact AIX SAN support. |
| 0x0000 0067 | Un-tagged cmd. (AIX tag missing) | contact AIX SAN support. |
| 0x0000 0068 | ||
| 0x0000 006C | An AIX internal eRAS eyecatcher check failed. | This is an AIX problem,contact AIX SAN support. |
| 0x0000 006D | ||
| 0x0000 006F | ||
| 0x0000 0072 | ||
| 0x0000 0073 | ||
| 0x0000 0079 | ||
| 0x0000 007A | ||
| 0x0000 007B | ||
| 0x0000 007C | ||
| 0x0000 008B | ||
| 0x0000 008C | ||
| 0x0000 008D | ||
| 0x0000 008E | ||
| 0x0000 008F | ||
| 0x0000 0091 | ||
| 0x0000 0092 | ||
| 0x0000 0076 | Size of iocb structure exceeds 1 page. | This is an AIX problem, contact AIX SAN support. |
| 0x0000 0077 | ||
| 0x0000 0081 | Software error setting up buffers. | This is an AIX problem, contact AIX SAN support. |
| 0x0000 0082 | ||
| 0x0000 0083 | Invalid parameter on EEH callback. | This is an AIX problem, contact AIX SAN support. |
| 0x0000 0084 | Failed to setup resources. This is an AIX problem, contact AIX support. | This is an AIX problem, contact AIX SAN support. |
| 0x0000 0085 | ||
| 0x0000 0086 | ||
| 0x0000 0087 | ||
| 0x0000 0088 | ||
| 0x0000 0080 | ||
| 0x0000 0071 | AIX has attempted to quiesce activity to the adapter unsuccessfully, | this is an AIX issue.with concurrent download, contact AIX SAN support. |
| 0x0000 0081 | Issued when a problem is discovered while setting up the host buffers. This is an AIX problem | This is an AIX problem, contact AIX SAN support. |
| 0x0000 0082 | Issued when a problem is discovered while setting up the host buffers. This is an AIX problem | This is an AIX problem, contact AIX SAN support. |
| 0x0000 00B0 | Login issues.. | Action plan depends on IOCB return code or local reject code |
| 0x0000 00B1 | ||
| 0x0000 00BA | ||
| 0x0000 0120 | A FARP has not been sent due to an error. | Action plan depends on IOCB return code or local reject code |
| 0x0000 0121 | AIX has received an un-anticipated IOCB. | contact AIX SAN support. |
| 0x0000 0123 | The AIX device driver does not have a free buffer to respond to a FARP from the SAN. | contact AIX SAN support. |
| 0x0000 0124 | The AIX device driver does not have a free entry in the login table. | contact AIX SAN support. |
| 0x0000 0125 | AIX software error allocating and mapping resources. | contact AIX SAN support. |